Skip to content

Expose TryGetDateTimeInput to be usable by custom filters#431

Merged
sebastienros merged 3 commits intosebastienros:mainfrom
Matthewsre:main
Jan 2, 2022
Merged

Expose TryGetDateTimeInput to be usable by custom filters#431
sebastienros merged 3 commits intosebastienros:mainfrom
Matthewsre:main

Conversation

@Matthewsre
Copy link
Copy Markdown
Contributor

I have a few custom filters in my solution for manipulating DateTime values and this would have been much easier if the TryGetDateTimeInput was made public or exposed.

I noticed there was another extension in this file and thought this would be a clean and simple approach that exposes this for custom filters in the Fluid.Filters namespace.

@hishamco
Copy link
Copy Markdown
Collaborator

I agree, it will be much cleaner if we move it to Fluid.Extensions folder and the namespace is Fluid.Values

…ss along with the private static values it depends on.
@Matthewsre
Copy link
Copy Markdown
Contributor Author

I created an Extensions folder in the Fluid project and tried adding a FluidValueExtensions class with the Fluid.Values namespace, but it was conflicting with an existing FluidValueExtensions class in the Values folder. I decided to move it into the existing FluidValueExtensions class.

Does this work for you, or would you prefer both the new and existing extension be moved into a new Extensions folder?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants